Network node, ims node and methods in a communications network

ABSTRACT

A method performed by a network node, for handling an outgoing media call of a user associated with multiple User Equipment, UEs, in a communications network is provided. The network node receives (402) a request for the outgoing media call to be set up from a first UE out of the multiple UEs. The request is obtained as a voice instruction 5 from the user via a Digital Assistant, DA, device. The voice instruction comprises a personalized name associated with the first UE. The network node further identifies (403) among the multiple UEs, the first UE and its associated IP Multimedia Subsystem, IMS, identifier based on the personalized name received in the voice instruction. The network node further sends (404), to an IMS node, the identified IMS identifier of the first UE and a 10 request to whether or not the first UE is registered in the IMS node and supports media When the first UE is registered in the IMS node and supports the media of the outgoing media call, the network node initiates (405) the outgoing media call from the first UE. When the first UE is not registered in the IMS node and/or does not support the media of the outgoing media call, the network node decides (406) how to 15 proceed with the outgoing media call.

TECHNICAL FIELD

Embodiments herein relate to a network node, an IMS node and a methodstherein. In particular, they relate to for handling an outgoing mediacall of a user associated with multiple User Equipments (UEs) in acommunications network.

BACKGROUND

In a typical wireless communication network, wireless devices, alsoknown as wireless communication devices, mobile stations, stations (STA)and/or user equipment (UE), communicate via a Local Area Network such asa WiFi network or a Radio Access Network (RAN) to one or more corenetworks (CN). The RAN covers a geographical area which is divided intoservice areas or cell areas, which may also be referred to as a beam ora beam group, with each service area or cell area being served by aradio network node such as a radio access node e.g., a Wi-Fi accesspoint or a radio base station (RBS), which in some networks may also bedenoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in 5thGeneration (5G). A service area or cell area is a geographical areawhere radio coverage is provided by the radio network node. The radionetwork node communicates over an air interface operating on radiofrequencies with the wireless device within range of the radio networknode. The radio network node communicates to the wireless device inDownLink (DL) and from the wireless device in UpLink (UL).

Specifications for the Evolved Packet System (EPS), also called a FourthGeneration (4G) network, have been completed within the 3rd GenerationPartnership Project (3GPP) and this work continues in the coming 3GPPreleases, for example to specify a Fifth Generation (5G) network alsoreferred to as 5G New Radio (NR). The EPS comprises the EvolvedUniversal Terrestrial Radio Access Network (E-UTRAN), also known as theLong Term Evolution (LTE) radio access network, and the Evolved PacketCore (EPC), also known as System Architecture Evolution (SAE) corenetwork. E-UTRAN/LTE is a variant of a 3GPP radio access network whereinthe radio network nodes are directly connected to the EPC core networkrather than to RNCs used in 3rd Generation (3G) networks. In general, inE-UTRAN/LTE the functions of a 3G RNC are distributed between the radionetwork nodes, e.g. eNodeBs in LTE, and the core network. As such, theRAN of an EPS has an essentially “flat” architecture comprising radionetwork nodes connected directly to one or more core networks, i.e. theyare not connected to RNCs. To compensate for that, the E-UTRANspecification defines a direct interface between the radio networknodes, this interface being denoted the X2 interface.

Multi-antenna techniques can significantly increase the data rates andreliability of a wireless communication system. The performance is inparticular improved if both the transmitter and the receiver areequipped with multiple antennas, which results in a Multiple-InputMultiple-Output (MIMO) communication channel. Such systems and/orrelated techniques are commonly referred to as MIMO.

In addition to faster peak Internet connection speeds, 5G planning aimsat higher capacity than current 4G, allowing higher number of mobilebroadband users per area unit, and allowing consumption of higher orunlimited data quantities in gigabyte per month and user. This wouldmake it feasible for a large portion of the population to streamhigh-definition media many hours per day with their mobile devices, whenout of reach of Wi-Fi hotspots. 5G research and development also aims atimproved support of machine to machine communication, also known as theInternet of things, aiming at lower cost, lower battery consumption andlower latency than 4G equipment.

Over-The-Top (OTT) services have been introduced allowing a third partytelecommunications service provider to provide services that aredelivered across an

Internet Protocol (IP) network. The IP network may e.g. be a publicinternet or cloud services delivered via a third party access network,as opposed to a carrier's own access network. OTT may refer to a varietyof services including communications, such as e.g. voice and/ormessaging, content, such as e.g. TV and/or music, and cloud-basedofferings, such as e.g. computing and storage.

A further OTT service is a Digital Assistant (DA). The DA may performtasks or services upon request from a user of a UE. The DA may beimplemented in several ways. A first way is commonly referred to as anoperator controlled DA. The operator controls the whole DA solutionwithout the UE being impacted. A user of the UE may provideinstructions, such as e.g. voice commands, to a core network node, suchas e.g. an IP Multimedia Subsystem (IMS) node, of the operator. Thevoice command may e.g. be “Digital Assistant, I want a pizza”, “DigitalAssistant, tell me how many devices are active right now”, “DigitalAssistant, set-up a conference”, or “Digital Assistant, how much creditdo I have?”. IMS is a general-purpose, open industry standard for voiceand multimedia communications over packet-based IP networks. It is acore network technology, that may serve as a low-level foundation fortechnologies like Voice over LTE (VoLTE) Voice over IP (VoIP),Push-To-Talk (PTT), Push-To-View, Video Calling, and Video Sharing.

The core network node may detect a hot word, which may also be referredto as a key word, indicating that the user is providing instructions tothe DA and may forward the instructions to a network node controlled bya third party service provider, the network node may e.g. comprise a DAplatform.

The DA platform may e.g. be a bot of a company providing a certainservice, such as e.g. a taxi service or a food delivery service. Theinstructions may be forwarded to the DA platform using e.g. a SessionInitiation Protocol/Real-time Transport Protocol

(SIP/RTP). The DA platform may comprise certain functionality, such ase.g. Speech to Text (Speech2Text), Identification of Intents & Entitiesand Control & Dispatch of Intents.

The DA platform may then forward the instructions to a further networknode, which may e.g. be an Application Server (AS) node, which hasaccess to the core network node via a Service Exposure ApplicationProgramming Interface (API). Thereby the DA may access the IMS node andperform services towards the core network node.

The DA platform is often required to pay a fee to the operator in orderto be reachable by the operator's DA users. The user may also berequired to pay fees to the operator and network provider for the usageof DA services. The operator may further be required to pay fees to thenetwork provider for every transaction performed via the ServiceExposure API.

A further way to implement the DA may be to provide the user with directaccess to the network node controlled by the third party serviceprovider comprising the DA platform. This may e.g. be done using adedicated UE having access to the first network node. This way ofimplementing the DA is commonly referred to as an OTT-controlled DA.

One of the services that can be invoked may e.g. be a telephony servicesor bot, implemented by the operator.

FIG. 1 depicts an architecture for an OTT-controlled DA, e.g. aTelephony Bot Architecture. A user 10 of a DA comprising a smart speaker20 may want to request actions, such as Call Bob, to an IMS network 30e.g. comprising VoLTE, via an API Gateway 40. If the request from thesmart speaker 20 user 10 needs some IMS capabilities, a OTT DA cloud 50will use service exposure capabilities to access to it. This may forexample be, when the user 10 asks to include a 3rd person to the call ormanipulate end user supplementary setting.

As mentioned above, A DA may handle communication via an API. In thecontext of an API, an intent is an abstract description of an operationto be performed. The text describing an intent and other aspects ofAPI:s, when used herein, is written with the text font Courier NewItalic.

In the case of an OTT-controlled DA, the DA may handle communication ofa user via an Open Mobile Alliance (OMA) API. In section 5.1.3.1 of theOpen Mobile Alliance™ specification, it is stated that for the OperationMake Call Session (Makecallsession) in the “OMA API Call Control andConfiguration”, an API may be invoked in order to set-up a call with auser or with a list of users. A Call Participants (CallParticipants)parameter comprises addresses of the participants involved in the call.

When an application invokes this OMA API, the network will setup a callamong all the specified participants.

SUMMARY

As a part of developing embodiments herein the inventors identified aproblem which first will be discussed.

As mentioned above, voice driven and/or hands-free use cases areincreasing in popularity. Typically, if a user wishes to make a anoutgoing call, it is done from one of the devices belonging to thatuser. This is true also in the cases where the user has multipledevices, such as e.g. a TV, phone, tablet etc. It is implicit whichdevice the user is using to perform the call.

There is today no way in an outgoing call to request a Digital Assistantto request a call to be initiated from a specific UE among the multipleUEs of a user.

There is no such exposure available today. The OMA standard list ofAPIs, for example, does not provide an operation to expose this action.The API MakeCallSession, mentioned above, does not include any parameterwith an identifier for the device from which the call is made.

An object of embodiments herein is improve the performance of acommunications network comprising multi device users using DAs.

According to an aspect of embodiments herein, the object is achieved bya method performed by a network node, for handling an outgoing mediacall of a user associated with multiple User Equipments, UEs, in acommunications network. The network node receives a request for theoutgoing media call to be set up from a first UE out of the multipleUEs. The request is obtained as a voice instruction from the user via aDigital Assistant, DA, device. The voice instruction comprises apersonalized name associated with the first UE.

The network node further identifies among the multiple UEs, the first UEand its associated IP Multimedia Subsystem, IMS, identifier based on thepersonalized name received in the voice instruction.

The network node further sends, to an IMS node, the identified IMSidentifier of the first UE and a request to whether or not the first UEis registered in the IMS node and supports media of the outgoing mediacall.

When the first UE is registered in the IMS node and supports the mediaof the outgoing media call, the network node initiates the outgoingmedia call from the first UE.

When the first UE is not registered in the IMS node and/or does notsupport the media of the outgoing media call, the network node decideshow to proceed with the outgoing media call.

According to another aspect of embodiments herein, the object isachieved by a method performed by an IMS node, for handling an outgoingmedia call of a user associated with at least one first User Equipment,UE, out of multiple UEs, in a communications network. The IMS nodereceives from a network node, an IMS identifier of the first UE and arequest to whether or not the first UE is registered in the IMS node andsupports media of the outgoing media call.

When the first UE is registered in the IMS node and supports the mediaof the outgoing media call, the IMS node terminates the outgoing mediacall from the first UE.

When the first UE is not registered in the IMS node and/or does notsupport the media of the outgoing media call, the IMS node sends aresponse to the network node, which response comprises a message thatthe media call cannot be terminated from the first UE.

According to a further aspect of embodiments herein, the object isachieved by a network node configured to handle an outgoing media callof a user associated with multiple UEs in a communications network. Thenetwork node is further configured to:

Receive a request for the outgoing media call to be set up from a firstUE out of the multiple UEs, which request is adapted to be obtained as avoice instruction from the user via a Digital Assistant, DA, device ,which voice instruction is adapted to comprise a personalized nameassociated with the first UE,

identify among the multiple UEs, the first UE and its associated IPMultimedia Subsystem, IMS, identifier based on the personalized nameadapted to be received in the voice instruction,

send to an IMS node, the identified IMS identifier of the first UE and arequest to whether or not the first UE is registered in the IMS node andis configured to support media of the outgoing media call,

when the first UE is registered in the IMS node and configured tosupport the media of the outgoing media call, initiate the outgoingmedia call from the first UE, and

when the first UE is not registered in the IMS node and/or is notconfigured to support the media of the outgoing media call, decide howto proceed with the outgoing media call.

According to a yet further aspect of embodiments herein, the object isachieved by an IMS node configured to handle an outgoing media call of auser associated with at least one first User Equipment, UE, out ofmultiple UEs, in a communications network. The IMS node is furtherconfigured to:

Receive from a network node, an IMS identifier of the first UE and arequest to whether or not the first UE is registered in the IMS node andis configured to support media of the outgoing media call,

when the first UE is registered in the IMS node and is configured tosupport the media of the outgoing media call, terminate the outgoingmedia call from the first UE, and

when the first UE is not registered in the IMS node and/or is notconfigured to support the media of the outgoing media call, send aresponse to the network node, which response is configured to comprise amessage that the media call cannot be terminated from the first UE.

An advantage of embodiments herein is that call initiation from a DAsmartspeaker or from a DA smartapp using voice control, e.g. in amulti-device scenario, is made possible. Thus, embodiments herein enablean implementation of cases with e.g. outgoing voice calls without theneed for interaction with an actual calling device, since they may bevoice driven via a DA.

Consequently, through the embodiments herein, the performance of acommunications network comprising multi device users using DAs isimproved.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of embodiments herein are described in more detail withreference to attached drawings in which:

FIG. 1 is a schematic block diagram illustrating prior art.

FIG. 2 is a schematic block diagram illustrating embodiments of acommunications network.

FIG. 3 is a schematic overview depicting embodiments of a method in thecommunications network.

FIG. 4 is a flowchart depicting embodiments of a method in a networknode.

FIG. 5 is a flowchart depicting embodiments of a method in an IMS node.

FIG. 6 is a schematic overview depicting embodiments of a method in thecommunications network.

FIG. 7 a and b are schematic block diagrams illustrating embodiments ofa network node.

FIG. 8 a and b are schematic block diagrams illustrating embodiments ofan IMS node.

FIG. 9 schematically illustrates a telecommunications network connectedvia an intermediate network to a host computer.

FIG. 10 is a generalized block diagram of a host computer communicatingvia a base station with a user equipment over a partially wirelessconnection.

FIGS. 11 to 14 are flowcharts illustrating methods implemented in acommunication system including a host computer, a base station and auser equipment.

DETAILED DESCRIPTION

Example embodiments herein may be based on an IMS network exposing anaction to initiate a call from a specific user's UE.

In some embodiments herein, exposing the action to initiate a call froma specific user's UE provides the following use case to be implemented:

Upon a user e.g. requesting the DA to call another user from a TV, theDA will request to an IMS node in the IMS network to fulfill the givenrequest via an exposed API. The IMS node may perform a check to verifywhether the UE is registered in the IMS node. The IMS node may alsoperform a check to verify whether the UE supports the specified media.

Example embodiments herein enables voice controlled selection of whichone of a user's multiple UEs that should be used for an outgoing call.Furthermore, embodiments herein e.g. enable voice controlled selectionof which media format that should be used for an outgoing call. Mediaformats may e.g. comprise audio and/or voice calls and video calls.

In some embodiments herein, an existing API may be updated, or, as analternative, a new API may be created. In an example embodiment, an OMAAPI MakeCallSession with parameters participants and callingDevice maybe defined. In such a new or updated API, the participants may bespecified by means of a userld which may be the IMS privateId. ThecallingDevice may be specified by means of a universally uniqueidentifier, uuid, representing the UE from which the user wants toinitiate the call. The returned value may be the result of theoperation, i.e. success or failure.

Embodiments herein provide a way to request a Digital Assistant torequest a call to be initiated from a specific UE among the multiple UEsthe user owns e.g. by means of an API according to embodiments herein.

According to some embodiments herein, therefore, a creating of a new APIor an update of the existing OMA API MakeCallSession is provided toinclude an IMS

Identifier, such as the UUID. This function may be performed by anapplication server, such as e.g. a Multimedia Telephony ApplicationServer, MTAS, IMS node 130. The MTAS IMS Node 130 would be suitable forexposing this function since it is the natural IMS node where the logicis to be placed, and it does not preclude other nodes forimplementation. A logic when used herein means a function that maps theindicated device to the IMS device identifier, i.e. couples an indicateddevice to an IMS identifier. An appropriate logic comprises theindication of the device the call is originated from.

Exposing the function may also be performed by any other IMS ApplicationServer handling calls.

FIG. 2 is a schematic overview depicting a wireless communicationsnetwork 100 wherein embodiments herein may be implemented. The wirelesscommunications network 100 comprises one or more RANs 104 and one ormore CNs 106. The wireless communications network 100 may use 5G NR butmay further use a number of other different technologies, such as,(LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA),Global System for Mobile communications/enhanced Data rate for GSMEvolution (GSM/EDGE), Worldwide Interoperability for Microwave Access(WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possibleimplementations.

Network nodes operate in the wireless communications network 100, suchas a radio network node 110 providing radio coverage.

The radio network node 110 provides radio coverage over a geographicalarea by means of antenna beams. The geographical area may be referred toas a cell, a service area, beam or a group of beams. The radio networknode 110 may be a transmission and reception point e.g. a radio accessnetwork node such as a base station, e.g. a radio base station such as aNodeB, an evolved Node B (eNB, eNode B), an NR Node B (gNB), a basetransceiver station, a radio remote unit, an Access Point Base Station,a base station router, a transmission arrangement of a radio basestation, a stand-alone access point, a Wireless Local Area Network(WLAN) access point, an Access Point Station (AP STA), an accesscontroller, a UE acting as an access point or a peer in a Device toDevice (D2D) communication, or any other network unit capable ofcommunicating with a UE within the cell served by the radio network node110 depending e.g. on the radio access technology and terminology used.

UEs such as a UEs 121, 122 and 123 operate in the wireless communicationnetwork 100. The UEs 121, 122, 123 may e.g. be a mobile station, anon-access point (non-AP) STA, a STA, a user equipment and/or a wirelessterminals, an NB-IoT device, an eMTC device and a CAT-M device, a WiFidevice, an LTE device and an NR device communicate via one or moreAccess Networks (AN), e.g. RAN, to one or more core networks (CN). Itshould be understood by the skilled in the art that “UE” is anon-limiting term which means any terminal, wireless communicationterminal, wireless device, Device to Device (D2D) terminal, or node e.g.smart phone, laptop, mobile phone, sensor, relay, mobile tablets,television units or even a small base station communicating within acell.

The CN further comprises an IP Multimedia Subsystem (IMS) node 130. TheIMS node 130 may be connected to a network node 150. The network node150 is represented by an Application Server (AS) node. The network node150 may be located in a cloud 101 as depicted in FIG. 1, in the CN or ina 3^(rd) Party domain of the communications network. The network node150 may act as a gateway to a platform node 151 located in a 3^(rd)Party domain of the communications network 100. Furthermore the IMS node130, the network node 150 and the platform node 151 may be collocatednodes, stand-alone nodes or distributed nodes comprised in a cloud 101,106. In some embodiments, the DA may comprise a DA device 125 and theplatform node 151. The DA device 125 may e.g. be a smart speaker. Theplatform node 151 may, as described above, be located in a third partydomain and be represented by e.g. be an OTT DA Cloud

It should be noted that although terminology from 3GPP LTE has been usedin this disclosure to exemplify the embodiments herein, this should notbe seen as limiting the scope of the embodiments herein to only theaforementioned system. Other wireless systems, including WCDMA, WiMax,UMB, GSM network, any 3GPP cellular network or any cellular network orsystem, may also benefit from exploiting the ideas covered within thisdisclosure.

The method will first be described from a helicopter perspective as asignalling diagram showing involved nodes such as the DA device 125, thenetwork node 150 and the IMS node 130 with reference to FIG. 3.Thereafter embodiments of the method as seen from the perspective of thenetwork node 150 and the IMS node 130, respectively, will beindividually described one by one with reference to FIGS. 4 and 5.

An example of a use case of embodiments herein is depicted in FIG. 3 andwill be explained by means of the following example scenario. Theactions in FIG. 3 are referred to in the text by their respectivereference signs in parentheses, e.g. (301).

A user A is a multi-device user who has, e.g. owns, multiple UEs 121,122, 123. The multiple UEs 121, 122, 123 may e.g. be a smartphone, afixed telephone and a TV. User A uses various media formats for makingcalls, such as e.g. voice (audio) and video calls. The calls may bereferred to as media calls, since they may be made using various mediaformats. The user A wants to call another user, user B, from a specificUE, such as the UE 121. The UE 121 may have video call capabilities and,in this example, user A wants to make a video call to user B.

To make a video call to the user B from the UE 121, the user A wouldprovide a voice instruction to the DA device 125. The user A may e.g.say “Digital assistant, make a video call to user B from the UE 121”. Inthe example scenario, the user A requests the digital assistant to setup a video call from the UE 121 to the user B and, thus, the DA device125 receives (301) a voice instruction from the user A.

The request is thereafter sent (302) to the network node 150. Therequest may be sent in a message, e.g. comprising identifiers for theintended participants in the call, the user B in the example scenario,and the device from which the call is to be initiated, the UE 121 in theexample scenario. The identifier for user B may be a personalized nameconfigured by the user A, or an IMS Public Identity, IMPU, correspondingto the user B. The nature of the identifier depends on where in thesystem the mapping of personalized names to corresponding digital IDs,such as IMPUs, is performed. The identifier for the UE 121 may be apersonalized name assigned to the UE 121 by user A, such as “TV”.

According to embodiments herein, the network node 150, having receivedthe request with the included IDs, performs (303) a mapping. Mapping maye.g. mean that the network node 150, knowing the personalized name, maye.g. check in a list to identify an ID corresponding to that particularpersonalized name. The result of the mapping is thus that an IMSidentifier corresponding to the personalized name is identified, i.e. anIMS identifier corresponding to the name “TV” for the UE 121 in theexample scenario. The IMS identifier may e.g. be a Universally UniqueIdentifier, UUID for the UE 121.

Thereafter, according to embodiments herein, a request is sent (304)form the network node 150 to the IMS node 130 to perform a check. Thecheck involves verifying if the requested UE 121 is registered in theIMS node 130 and if it supports the requested media format. In theexample scenario, the request would be to check whether the UE 121 isregistered in the IMS node 130 and supports video calls.

Having received the request, the IMS node 130 performs the requestedcheck (305). If the result of the check is that the requested UE isregistered and supports the requested format, the call may be terminated(306). In the example scenario, if the UE 121 is registered and supportsvideo call, the requested video call may be successfully set up betweenuser A and user B, from the UE 121, i.e. the “TV”. A response may alsobe sent back to the network node 150 indicating that the operation wassuccessful.

If, on the other hand, the result of the check is that the requested UE121 is not registered in the IMS node and/or does not support therequested format, the call cannot be terminated. A response maytherefore be sent (307) back to the network node 150.

The response may comprise a message that the operation was notsuccessful with the given parameters. In the example scenario, themessage is sent that either the IMS identifier for UE 121 is notregistered in the IMS node 130 and/or that UE 121 does not support therequested media format.

The network node 150 may then decide (308) how to proceed with theprocess of setting up the call.

In some embodiments herein, the network node 150 will send a response(309) to the DA device 125 indicating the result of the operation asrequested. Furthermore, the message may include instructions for how toproceed with handling the requested media call, in accordance with whathas been decided by the network node. In the example scenario theresponse may comprise instructing the DA device 125 to tell user A thatthe UE 121 was not accepted for the requested call.

Having received the response from the network node 150, the DA device125 may have been instructed to ask (310) user A to provide new oradditional instructions for how to handle the requested media call. Inthe example scenario, the DA device 125 may ask the user A to select analternative device from which to call, such as from the UE 122. Thealternative device may be referred to by the UE with the personalizedname so that it is recognizable to the user A. Consequently, in order toenable this, a mapping between personalized names among the multiple UEs121, 122, 123 associated with user A may have been previously performed.

Alternatively, the DA device 125 may ask user A to select an alternativemedia format for the requested media call.

Thereafter, the flow according to FIG. 3 may be repeated until asuccessful operation has been performed and a media call may beterminated between user A and user B.

To enable the process shown in FIG. 3, the IMS node 130 may expose anAPI to network node 150. As mentioned above, in some embodiments herein,the API MakeCallSession may be used with parameters participants, andcallingDevice. The participants may be specified by means of a userldwhich may be the IMS privateId. andthe callingDevice may be specified bymeans of the uuid representing the UE from which the user wants toinitiate the call.

Using the example embodiment depicted in FIG. 3 and explained above, anexample use case for the above API may be explained as follows.

In the example embodiment, the OMA API MakeCallSession may be altered tofit the desired operation. A MakeCallSession request is to be made,which requires input parameters. These parameters may be expressed asparticipants and callingDevice.

The Participants parameter may represent one or more users that shouldreceive the outgoing call. In this example embodiment, there is only oneparticipant—the user B. The user B may be identified with a userld,which for the purpose of MakeCallSession is the publicId which may behis/her allocated IMPU. The IMPU is a unique permanently allocatedglobal identity assigned by the home network operator.

The callingDevice parameter may be the UE that is intended to be usedfor the call. In this example embodiment, the callingDevice is the UE121. The callingDevice may be identified using an IMS identifier, suchas the UUID) associated with that device.

In order to translate the UE name employed by the user to an IMSidentifier, the DA system may be configured so that there is a mappingbetween a device ID of the UE, such as the IMS identifier, and apersonalized name associated with that UE: The personalized name is thename that is said by the user in the voice instruction to the DA device125. In the example embodiment, the personalized name for the requestedUE, UE121, may e.g. be “TV”.

Thus, in the example embodiment, the MakeCallSession would be given theparameters:

the IMPU corresponding to the user B, and

the IMS identifier corresponding to the UE 121, which user A calls “TV”.

In some embodiments, it may be possible that the operator has a mappingbetween the IMS identifier and the personalized name for a user'sdevices. The operator may for example have registered that<urn:uuid:6ba7b810-9dad-11d1-80b4-00c04fd430c4> corresponds to thespoken words “Living room TV”. Furthermore, the user may use the UUIDfor the device instead of assigning a personalized name.

Example embodiments of a method performed by the first network node 150,for handling an outgoing media call of a user A associated with themultiple UEs, 121, 122, 123 in a communications network 100, will now bedescribed with reference to a flowchart depicted in FIG. 4.

The first network node 150 may be represented by an application servernode. The method comprises the following actions, which actions may betaken in any suitable order. Actions that are optional are presented indashed boxes in FIG. 4.

Action 401

In order to facilitate a mapping between personalized names for themultiple UEs and their corresponding IMS identifiers, the DA device 125may first be configured by the user.

In an example scenario herein, the user A is associated with multipledevices: UEs 121, 122 and 123. The configuration, which may be anautomatic configuration phase, when exemplified with the scenarioinvolving user A may comprise the following:

-   -   User A sets up the DA device 125 to manage his/her IMS devices,        i.e. UEs 121, 122, 123.    -   The DA device 125 triggers an application server, such as the        MTAS, to start a set up phase.    -   One by one, each device may ring, optionally employing a special        tone so that the device is easily identified.    -   User A instructs the DA device 125 what personalized name he/she        wants to allocate to the alerted UE 121, 122, 123, such as “my        cellphone”, “TV”, “old phone” etc.    -   A set-up completion may be performed, optionally involving dummy        test calls. When the set-up is completed, the DA device 125 is        configured so that the personalized names employed by the user A        are coupled with digital identifiers that may be employed by the        various nodes in the communications network 100.

In some embodiments, when a user is associated with multiple personas,such as “work”, “family” etc., the configuration may further includecoupling personalized names for each out of the multiple personas with adigital identifier. These identifiers may then be employed by thevarious nodes in the communications network 100, in a scenario when auser requests to set up a call using a specific persona.

Action 402

The network node 150 receives a request for the outgoing media call tobe set up from a first UE 121 out of the multiple UEs 121, 122, 123. Therequest is obtained as a voice instruction from the user A via theDigital Assistant, DA, device 125. The voice instruction comprises apersonalized name associated with the first UE 121.

The request for the outgoing media call to be set up from the first UE121 out of the multiple UEs 121, 122, 123 may further comprise anindication of a media format of the media to be used in the outgoingmedia call. The media format may be specified by the user A in the voiceinstruction.

Furthermore, the request obtained as a voice instruction from the firstuser A may further comprise a request for the outgoing call to be set upvia a first persona out of multiple personas associated with the firstuser A. The voice instruction may further comprise a personalized nameassociated with the first persona of the first user A.

Action 403

After the network node 150 has received the request from the user viathe DA device 125, the network node identifies among the multiple UEs121, 122, 123, the first

UE 121 and its associated IMS identifier based on the personalized namereceived in the voice instruction.

Additionally, identifying may in some embodiments further compriseidentifying among the multiple personas associated with the first userA, an IMS user ID based on the personalized name associated with thefirst persona of the first user A received in the voice instruction.

Action 404

When the IMS identifier of the first UE 121 has been identified, thenetwork node 150 sends the identified IMS identifier to the IMS node130. The network node also sends and a request to the IMS node 130 tocheck whether or not the first UE 121 is registered in the IMS node 130and supports media of the outgoing media call. The media of the outgoingmedia call may e.g. be audio/voice or video.

In some embodiments herein, when an IMS user ID based on thepersonalized name associated with the first persona of the first user Ahas been identified, the identified IMS user ID may be sent by thenetwork node 150 to the IMS node 130.

Action 405

After having received a request to perform the check to see whether ornot the first UE 121 is registered in the IMS node 130 and supportsmedia of the outgoing media call, the IMS node 130 sends a response tothe network node 150 indicating the result of the check.

Thus, when the first UE 121 is registered in the IMS node 130 andsupports the media of the outgoing media call, the network node 150 isinformed of this by the IMS node 130. The network node 150 theninitiates the outgoing media call from the first UE 121. The initiationmay comprise sending a request to the IMS node to terminate the outgoingmedia call.

Action 406

After having received the request and performed the check to see whetheror not the first UE 121 is registered in the IMS node 130 and supportsmedia of the outgoing media call, the IMS node 130 sends a response tothe network node 150 indicating the result of the check.

Thus, when the first UE 121 is not registered in the IMS node 130 and/ordoes not support the media of the outgoing media call, the network node150 may be informed of this by the IMS node 130. The network node 150then decides how to proceed with the outgoing media call.

According to some embodiments herein, deciding how to proceed with theoutgoing media call may comprise one of:

Instructing the DA device 125 to offer the user to set up the outgoingmedia call on a second UE 122 out of the multiple UEs 121, 122, 123;

instructing the DA device 125 to request the user to select analternative UE among the multiple UEs 121, 122, 123 to set up theoutgoing media call; or

instructing the DA device 125 to tell the user 120 that the pick-up ofthe incoming media call on the first UE 121 is not possible.

Method in the IMS node 130

Example embodiments of a method performed by the IMS node 130, forhandling an outgoing media call of the user A associated with at leastone first UE 121 out of multiple UEs 121, 122, 123 in a communicationsnetwork 100 will now be described with reference to a flowchart depictedin FIG. 5.

The method comprises the following actions, which actions may be takenin any suitable order. Actions that are optional are presented in dashedboxes in FIG. 5.

Action 501

In order to facilitate handling of an upcoming outgoing media call, theIMS node 130 may expose an API to the network node 150. The APIcomprises parameters associated with making a call session related tothe upcoming outgoing media call, and requests at least IMS identifiersof the UEs 121, 122, 123.

The wording to expose when used herein, means to make accessible, suchas e.g. to provide access to authorized clients to the networkcapabilities via an API.

The parameters of the API may e.g. comprise any one out of: intendedparticipants in the media call, defined by corresponding User IDs; andthe respective IMS identifier defining any one out of the multiple UEs121, 122, 123.

The User ID for the intended participants may correspond to an IMSPublic Identity (IMPU) and the respective IMS identifier for any one outof the multiple UEs 121, 122, 123 may be a Universally Unique Identifier(UUID) for the respective UE.

Action 502

For handling an outgoing media call of the user A associated with atleast one first UE 121 out of multiple UEs 121, 122, 123, the IMS node130 first receives an IMS identifier of the first UE 121 and a requestfrom a network node 150. The request comprises to check whether or notthe first UE 121 is registered in the IMS node 130 and supports media ofthe outgoing media call.

In some embodiments herein, the IMS node 130 may further receive an IMSuser ID associated with a first persona of the first user A and arequest to check whether or not the first persona of the first user A isregistered in the IMS node 130 and supports the outgoing media call.This check may e.g. be performed via service exposure, i.e. an APIexposed by the IMS, for example by the MTAS.

Action 503

After having performed the check to see whether or not the first UE 121is registered in the IMS node 130 and supports media of the outgoingmedia call, the IMS node 130 takes an action depending on the outcome ofthe check.

If the result of the check is that the first UE 121 is registered in theIMS node 130 and supports the media of the outgoing media call, the IMSnode 130 terminates the outgoing media call from the first UE 121. TheIMS node 130 may also send a response to the network node 150 indicatingthat the outgoing media call may be terminated with the given IMSidentifier.

In some embodiments herein, the IMS node 130 may further have receivedan IMS user ID associated with a first persona of the first user A. TheIMS node may then further check whether or not the first persona of thefirst user A is registered in the IMS node 130 and supports the outgoingmedia call. This check may e.g. be performed via service exposure, i.e.an API exposed by IMS, for example by the MTAS.

In such an embodiment, the outgoing media call may be terminated, by theIMS node 130, from the first UE 121 using the first persona if:

The first UE 121 is registered in the IMS node 130 and supports themedia of the outgoing media call; and

the first persona of the first user A is registered in the IMS node 130and supports the outgoing media call.

Action 504

If, on the other hand, the outcome of the abovementioned check is thatthe first UE 121 is not registered in the IMS node 130 and/or does notsupport the media of the outgoing media call, the IMS node 130 sends aresponse to the network node 150. The response comprises a messageinforming the network node that the operation was not successful andthat, therefore, the media call cannot be terminated from the first UE121, i.e. with the given IMS identifier.

In some embodiments herein, if the check in the IMS node 130 as shownthat a call may not be terminated, by the IMS node 130, from the firstUE 121 using the first persona, then the response to network node 150may further comprise a message that the media call cannot be terminatedfrom the first UE 121 using the first persona.

Embodiments herein such as mentioned above will now be further describedand exemplified. The text below is applicable to and may be combinedwith any suitable embodiment described above.

A further example of an additional use case of embodiments herein isdepicted in FIG. 6 and will be explained by means of the followingexample scenario.

In the scenario depicted in FIG. 6, the user A wishes to set up a callwith the user B, similarly to the example scenario depicted in theflowchart in FIG. 3. In FIG. 6 however, in addition to being associatedwith multiple UEs 121, 122, 123, the user A is also associated withmultiple personas P1, P2 etc.

A persona when used herein refers to a persona in the IMS domain whichmay be a phone number associated with a user's role in life. Forexample, a user may have one phone number for private use and anotherone for business purposes. In the example scenario, the user A wants tocall the other user B from a specific UE out of the multiple UEs andusing a specific persona out of the multiple personas. The user A maye.g. want to call the user B from UE 121 using a first persona, P1. Asmentioned above, user A may also request a specific media format to beused for the call. In the example scenario, the user A wishes to make avideo call from the first UE 121 using the first persona, P1.

To make a video call to the user B from UE 121 using the first personaP1, user A would provide a voice instruction to the DA device 125. Theuser A may e.g. say “Digital assistant, make a video call to user B fromthe UE 121 as persona P1”. The digital assistant device would thenconvey the request to the network node 150, which may be done via aplatform node 151.

The network node 150 may then perform a mapping in a similar fashion towhat has been described in embodiments above. In this scenario however,the personalized name that user A employs for the first persona P1 mayalso be mapped to an IMS identifier corresponding to that personalizedname. Such an IMS identifier may be referred to as an IMS user ID, asmentioned above. The IMS user ID may e.g. be a telephone number or aSession Initiation Protocol, SIP, identity.

Furthermore, when the request is sent from the network node 150 to theIMS node 130 to perform a check, the check may additionally involveverifying if the requested IMS user ID is registered in the IMS node 130and supports the outgoing media call. There may be several reasons whyan outgoing media call may not be supported by a specific persona. Suchreasons may e.g. be if the user has configured the persona in such away. A company may e.g. not allow a user to make outgoing calls fromhis/her business persona after office hours.

In the example scenario, the request would be to check whether:

-   -   The UE 121 is registered in the IMS node 130 and supports video        calls, and    -   the first persona P1 is registered in the IMS node 130 and the        outgoing call.

Only if both checks generate a positive result may the outgoing call beterminated. This means that the call cannot be terminated from aregistered UE that supports a requested media format if the requestedpersona is not registered in the IMS node and/or does not support theoutgoing call. In the example scenario, the requested persona P1 maye.g. not support calling the user B if user B is a family contact andthe first persona P1 is a work persona.

Another example of when the outgoing call may not be supported may bethat calling the user B means setting up an international call as thefirst persona P1, which may not be permitted. This restriction imposedon the first persona P1 would be known to the IMS node 130, and the IMSnode 130 would therefore send a response to the network node 150 thatterminating the call was not possible with the given identities.

In the example scenario, if the persona P1 is registered in the IMS node130 and supports the outgoing call, the call may be terminated as longas the UE 121 is registered in the IMS node 130 and supports videocalls. In such a scenario, the video call may be set up from the user A,as the first persona P1 using the first UE 121, to the user B.

On the other hand, if the call could not be terminated, the network node150 may then decide how to proceed with the process of setting up thecall. This process is similar to the example scenario depicted FIG. 3,with adequate changes to accommodate the additional possibilitiesprovided by the multiple personas. The DA device 125 may e.g. ask theuser A to select an alternative persona for the requested media call.

It should be noted that many combinations of possibilities for theinteraction between the DA device 125 and the user are available, andthat the choices of actions to take following an unsuccessful operationto terminate a call are by no means limited to those exemplified.

Following an unsuccessful attempt to terminate a call from a specificdevice, such as the first UE 121 using a specified persona, the flow ofinteraction described here and depicted in FIG. 6 may be repeated untila successful operation has been performed and a media call may beterminated between the user A and the user B.

To perform the method actions above for handling an outgoing media callof a user A associated with multiple pieces of User Equipment, UEs, 121,122, 123 in a communications network 100, the network node 150 maycomprise the arrangement depicted in FIG. 7a and FIG. 7 b.

The network node 150 may be adapted to be represented by an applicationserver node.

The network node 150 may comprise an input and output interface 700depicted in FIG. 7a , configured to communicate e.g. with the IMS node130. The input and output interface 700 may comprise a wireless receivernot shown and a wireless transmitter not shown.

The network node 150 may be configured to, e.g. by means of aconfiguring unit 720 in the network node 150 depicted in FIG. 7b ,initiate a configuration of the DA device.

The network node 150 may further be configured to receive, e.g. by meansof a receiving unit 730 in the network node 150 depicted in FIG. 7b , arequest for the outgoing media call to be set up from a first UE 121 outof the multiple UEs 121, 122, 123, which request is adapted to beobtained as a voice instruction from the user A via a Digital Assistant,DA, device 125, which voice instruction is adapted to comprise apersonalized name associated with the first UE 121.

The request for the outgoing media call to be set up from the first UE121 out of the multiple UEs 121, 122, 123 may be further configured tocomprise an indication of a media format of the media in the outgoingmedia call, which media format is adapted to be specified by the user Ain the voice instruction.

The network node 150 may further be configured to identify, e.g. bymeans of an identifying unit 740 in the network node 150 depicted inFIG. 7b , among the multiple UEs 121, 122, 123, the first UE 121 and itsassociated IP Multimedia Subsystem, IMS, identifier based on thepersonalized name adapted to be received in the voice instruction. Thenetwork node 150 may further be configured to identify, e.g. by means ofthe identifying unit 740 in the network node 150 depicted in FIG. 7b ,among the multiple personas associated with the first user A, an IMSuser ID based on the personalized name associated with the first personaof the first user A adapted to be received in the voice instruction.

The network node 150 may further be configured to send, e.g. by means ofa sending unit 750 in the network node 150 depicted in FIG. 7b , to anIMS node 130, the identified IMS identifier of the first UE 121 and arequest to whether or not the first UE 121 is registered in the IMS node130 and is configured to support media of the outgoing media call.

The request sent to the IMS node 130 may further be adapted to comprisea request for the outgoing call to be set up via a first persona out ofmultiple personas associated with the first user A, and wherein thevoice instruction is further adapted to comprise a personalized nameassociated with the first persona of the first user A. The network node150 may further be configured to send, e.g. by means of the sending unit750 in the network node 150 depicted in FIG. 7b , the identified IMSuser ID to the IMS node 130.

When the first UE 121 is registered in the IMS node 130 and configuredto support the media of the outgoing media call, the network node 150may further be configured to initiate, e.g. by means of an initiatingunit 760 in the network node 150 depicted in FIG. 7b , the outgoingmedia call from the first UE 121.

When the first UE 121 is not registered in the IMS node 130 and/or isnot configured to support the media of the outgoing media call, thenetwork node 150 may further be configured to decide, e.g. by means of adeciding unit 770 in the network node 150 depicted in FIG. 7b , how toproceed with the outgoing media call.

The network node 150 may decide to instruct, e.g. by means of aninstructing unit 780 in the network node 150 depicted in FIG. 7b , theDA device 125 to offer the user to set up the outgoing media call on asecond UE 122 out of the multiple UEs 121, 122, 123.

The network node 150 may further decide to instruct, e.g. by means ofthe instructing unit 780 in the network node 150 depicted in FIG. 7b ,the DA device 125 to request the user to select an alternative UE amongthe multiple UEs 121, 122, 123 to set up the outgoing media call.

The network node 150 may further decide to instruct, e.g. by means ofthe instructing unit 780 in the network node 150 depicted in FIG. 7b ,the DA device 125 to tell the user 120 that the pick-up of the incomingmedia call on the first UE 121 is not possible

The embodiments herein may be implemented through a respective processoror one or more processors, such as a processor 715 of a processingcircuitry in the network node 150 depicted in FIG. 7a , together with arespective computer program code for performing the functions andactions of the embodiments herein. The program code mentioned above mayalso be provided as a computer program product, for instance in the formof a data carrier carrying computer program code for performing theembodiments herein when being loaded into the network node 150. One suchcarrier may be in the form of a CD ROM disc. It is however feasible withother data carriers such as a memory stick. The computer program codemay furthermore be provided as pure program code on a server anddownloaded to the network node 150.

The network node 150 may further comprise a memory 710 comprising one ormore memory units to store data on. The memory comprises instructionsexecutable by the processor 715. The memory 710 is arranged to be usedto store e.g. identifiers, IMS identifiers, configurations andapplications to perform the methods herein when being executed in thenetwork node 150.

Those skilled in the art will also appreciate that the units in thenetwork node 150 mentioned above may refer to a combination of analogueand digital circuits, and/or one or more processors configured withsoftware and/or firmware, e.g. stored in the network node 150 that whenexecuted by the respective one or more processors such as the processorsdescribed above. One or more of these processors, as well as the otherdigital hardware, may be included in a single Application-SpecificIntegrated Circuitry (ASIC), or several processors and various digitalhardware may be distributed among several separate components, whetherindividually packaged or assembled into a system-on-a-chip (SoC).

In some embodiments, a computer program 790 comprises instructions,which when executed by the respective at least one processor 715, causethe at least one processor 715 of the network node 150 to perform theactions above.

In some embodiments, a carrier 795 comprises the computer program 790,wherein the carrier 795 is one of an electronic signal, an opticalsignal, an electromagnetic signal, a magnetic signal, an electricsignal, a radio signal, a microwave signal, or a computer-readablestorage medium.

To perform the method actions above for handling an outgoing media callof a user A associated with at least one first User Equipment, UE, 121out of multiple UEs 121, 122, 123 in a communications network 100, theIMS node 130 may comprise the arrangement depicted in FIG. 8a and FIG. 8b.

The IMS node 130 may comprise an input and output interface 800 depictedin FIG. 8a , configured to communicate e.g. with the network node 150.The input and output interface 800 may comprise a wireless receiver notshown and a wireless transmitter not shown.

The IMS node 130 may be configured to expose, e.g. by means of anexposing unit 820 in the IMS node 130 depicted in FIG. 8b , to thenetwork node 150, an Application Program Interface, API, configured tocomprise parameters associated with making a call session related to theupcoming outgoing media call and adapted to request at least IMSidentifiers of the UEs 121, 122, 123.

The API parameters may be adapted to comprise any one out of intendedparticipants in the media call adapted to be defined by correspondingUser Identities, User IDs, wherein the User ID is adapted to correspondto an IMS Private Identity, IMS Private ID, and/or the respective IMSidentifier adapted to define any one out of the multiple UEs 121, 122,123.

The respective IMS identifier for any one out of the multiple UEs 121,122, 123 may be adapted to be a Universally Unique Identifier, UUID, forthe respective UE out of the multiple UEs 121, 122, 123.

The IMS node 130 is configured to receive, e.g. by means of a receivingunit 830 in the IMS node 130 depicted in FIG. 8b , from a network node150, an IMS identifier of the first UE 121 and a request to whether ornot the first UE 121 is registered in the IMS node and is configured tosupport media of the outgoing media call.

When the first UE 121 is registered in the IMS node and is configured tosupport the media of the outgoing media call, the IMS node 130 isfurther configured to terminate, e.g. by means of a terminating unit 840in the IMS node 130 depicted in FIG. 8b , the outgoing media call fromthe first UE 121.

When the first UE 121 is not registered in the IMS node and/or is notconfigured to support the media of the outgoing media call, the IMS node130 is further configured to send, e.g. by means of a sending unit 850in the IMS node 130 depicted in FIG. 8b , a response to the network node150, which response is configured to comprise a message that the mediacall cannot be terminated from the first UE 121.

The IMS node 130 may be further configured to receive from the networknode 150, e.g. by means of the receiving unit 830 in the IMS node 130depicted in FIG. 8b , an IMS user ID configured to be associated with afirst persona of the first user A, and a request to whether or not thefirst persona of the first user A is registered in the IMS node 130 andis configured to support the outgoing media.

The IMS node 130 may be further configured to terminate, e.g. by meansof the terminating unit 840 in the IMS node 130 depicted in FIG. 8b ,the outgoing media call from the first UE 121 using the first persona,when the first UE 121 is registered in the IMS node and supports themedia of the outgoing media call, and when the first persona of thefirst user A is registered in the IMS node and supports the outgoingmedia call.

When the first UE 121 is not registered in the IMS node and/or does notsupport the media of the outgoing media call and/or when the firstpersona of the first user A is not registered in the IMS node and/ordoes not support the outgoing media call, the IMS node 130 may befurther configured to send, e.g. by means of the sending unit 850 in theIMS node 130 depicted in FIG. 8b , a response to the network node 150,which response is adapted to comprise a message that the media callcannot be terminated from the first UE 121 using the first persona.

The embodiments herein may be implemented through a respective processoror one or more processors, such as a processor 815 of a processingcircuitry in the IMS node 130 depicted in FIG. 8a , together with arespective computer program code for performing the functions andactions of the embodiments herein. The program code mentioned above mayalso be provided as a computer program product, for instance in the formof a data carrier carrying computer program code for performing theembodiments herein when being loaded into the IMS node 130. One suchcarrier may be in the form of a CD ROM disc. It is however feasible withother data carriers such as a memory stick. The computer program codemay furthermore be provided as pure program code on a server anddownloaded to the IMS node 130.

The IMS node 130 may further comprise a memory 810 comprising one ormore memory units to store data on. The memory comprises instructionsexecutable by the processor 815. The memory 810 is arranged to be usedto store e.g. identifiers, IMS identifiers, configurations andapplications to perform the methods herein when being executed in theIMS node 130.

Those skilled in the art will also appreciate that the units in the IMSnode 130 mentioned above may refer to a combination of analogue anddigital circuits, and/or one or more processors configured with softwareand/or firmware, e.g. stored in the IMS node 130 that when executed bythe respective one or more processors such as the processors describedabove. One or more of these processors, as well as the other digitalhardware, may be included in a single Application-Specific IntegratedCircuitry (ASIC), or several processors and various digital hardware maybe distributed among several separate components, whether individuallypackaged or assembled into a system-on-a-chip (SoC).

In some embodiments, a computer program 890 comprises instructions,which when executed by the respective at least one processor 815, causethe at least one processor 815 of the IMS node 130 to perform theactions above.

In some embodiments, a carrier 895 comprises the computer program 890,wherein the carrier 895 is one of an electronic signal, an opticalsignal, an electromagnetic signal, a magnetic signal, an electricsignal, a radio signal, a microwave signal, or a computer-readablestorage medium.

Further Extensions and Variations

With reference to FIG. 9, in accordance with an embodiment, acommunication system includes a telecommunication network 3210 such asthe wireless communications network 100, e.g. a NR network, such as a3GPP-type cellular network, which comprises an access network 3211, suchas a radio access network, and a core network 3214. The access network3211 comprises a plurality of base stations 3212 a, 3212 b, 3212 c, suchas the radio network node 110, access nodes, AP STAs NBs, eNBs, gNBs orother types of wireless access points, each defining a correspondingcoverage area 3213 a, 3213 b, 3213 c. Each base station 3212 a, 3212 b,3212 c is connectable to the core network 3214 over a wired or wirelessconnection 3215. A first user equipment (UE) e.g. the wireless devices120 such as a Non-AP STA 3291 located in coverage area 3213 c isconfigured to wirelessly connect to, or be paged by, the correspondingbase station 3212 c. A second UE 3292 e.g. the first or second radionode 110, 120 or such as a Non-AP STA in coverage area 3213 a iswirelessly connectable to the corresponding base station 3212 a.

While a plurality of UEs 3291, 3292 are illustrated in this example, thedisclosed embodiments are equally applicable to a situation where a soleUE is in the coverage area or where a sole UE is connecting to thecorresponding base station 3212.

The telecommunication network 3210 is itself connected to a hostcomputer 3230, which may be embodied in the hardware and/or software ofa standalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. The host computer 3230 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider. Theconnections 3221, 3222 between the telecommunication network 3210 andthe host computer 3230 may extend directly from the core network 3214 tothe host computer 3230 or may go via an optional intermediate network3220. The intermediate network 3220 may be one of, or a combination ofmore than one of, a public, private or hosted network; the intermediatenetwork 3220, if any, may be a backbone network or the Internet; inparticular, the intermediate network 3220 may comprise two or moresub-networks (not shown).

The communication system of FIG. 9 as a whole enables connectivitybetween one of the connected UEs 3291, 3292 and the host computer 3230.The connectivity may be described as an over-the-top (OTT) connection3250. The host computer 3230 and the connected UEs 3291, 3292 areconfigured to communicate data and/or signaling via the OTT connection3250, using the access network 3211, the core network 3214, anyintermediate network 3220 and possible further infrastructure (notshown) as intermediaries. The OTT connection 3250 may be transparent inthe sense that the participating communication devices through which theOTT connection 3250 passes are unaware of routing of uplink and downlinkcommunications. For example, a base station 3212 may not or need not beinformed about the past routing of an incoming downlink communicationwith data originating from a host computer 3230 to be forwarded (e.g.,handed over) to a connected UE 3291. Similarly, the base station 3212need not be aware of the future routing of an outgoing uplinkcommunication originating from the UE 3291 towards the host computer3230.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 10. In a communicationsystem 3300, a host computer 3310 comprises hardware 3315 including acommunication interface 3316 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of the communication system 3300. The host computer 3310 furthercomprises processing circuitry 3318, which may have storage and/orprocessing capabilities. In particular, the processing circuitry 3318may comprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. The host computer3310 further comprises software 3311, which is stored in or accessibleby the host computer 3310 and executable by the processing circuitry3318. The software 3311 includes a host application 3312. The hostapplication 3312 may be operable to provide a service to a remote user,such as a UE 3330 connecting via an OTT connection 3350 terminating atthe UE 3330 and the host computer 3310. In providing the service to theremote user, the host application 3312 may provide user data which istransmitted using the OTT connection 3350.

The communication system 3300 further includes a base station 3320provided in a telecommunication system and comprising hardware 3325enabling it to communicate with the host computer 3310 and with the UE3330. The hardware 3325 may include a communication interface 3326 forsetting up and maintaining a wired or wireless connection with aninterface of a different communication device of the communicationsystem 3300, as well as a radio interface 3327 for setting up andmaintaining at least a wireless connection 3370 with a UE 3330 locatedin a coverage area (not shown in FIG. 10) served by the base station3320. The communication interface 3326 may be configured to facilitate aconnection 3360 to the host computer 3310. The connection 3360 may bedirect or it may pass through a core network (not shown in FIG. 10) ofthe telecommunication system and/or through one or more intermediatenetworks outside the telecommunication system. In the embodiment shown,the hardware 3325 of the base station 3320 further includes processingcircuitry 3328, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The base station 3320 further has software 3321 stored internally oraccessible via an external connection.

The communication system 3300 further includes the UE 3330 alreadyreferred to. Its hardware 3335 may include a radio interface 3337configured to set up and maintain a wireless connection 3370 with a basestation serving a coverage area in which the UE 3330 is currentlylocated. The hardware 3335 of the UE 3330 further includes processingcircuitry 3338, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The UE 3330 further comprises software 3331, which is stored in oraccessible by the UE 3330 and executable by the processing circuitry3338. The software 3331 includes a client application 3332. The clientapplication 3332 may be operable to provide a service to a human ornon-human user via the UE 3330, with the support of the host computer3310. In the host computer 3310, an executing host application 3312 maycommunicate with the executing client application 3332 via the OTTconnection 3350 terminating at the UE 3330 and the host computer 3310.In providing the service to the user, the client application 3332 mayreceive request data from the host application 3312 and provide userdata in response to the request data. The OTT connection 3350 maytransfer both the request data and the user data. The client application3332 may interact with the user to generate the user data that itprovides.

It is noted that the host computer 3310, base station 3320 and UE 3330illustrated in FIG. 10 may be identical to the host computer 3230, oneof the base stations 3212 a, 3212 b, 3212 c and one of the UEs 3291,3292 of FIG. 9, respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 10 and independently, thesurrounding network topology may be that of FIG. 9.

In FIG. 10, the OTT connection 3350 has been drawn abstractly toillustrate the communication between the host computer 3310 and the useequipment 3330 via the base station 3320, without explicit reference toany intermediary devices and the precise routing of messages via thesedevices. Network infrastructure may determine the routing, which it maybe configured to hide from the UE 3330 or from the service provideroperating the host computer 3310, or both. While the OTT connection 3350is active, the network infrastructure may further take decisions bywhich it dynamically changes the routing (e.g., on the basis of loadbalancing consideration or reconfiguration of the network).

The wireless connection 3370 between the UE 3330 and the base station3320 is in accordance with the teachings of the embodiments describedthroughout this disclosure. One or more of the various embodimentsimprove the performance of OTT services provided to the UE 3330 usingthe OTT connection 3350, in which the wireless connection 3370 forms thelast segment. More precisely, the teachings of these embodiments mayimprove the data rate, latency, power consumption and thereby providebenefits such as user waiting time, relaxed restriction on file size,better responsiveness, extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring the OTT connection 3350 between the hostcomputer 3310 and UE 3330, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring the OTT connection 3350 may be implemented in the software3311 of the host computer 3310 or in the software 3331 of the UE 3330,or both. In embodiments, sensors (not shown) may be deployed in or inassociation with communication devices through which the OTT connection3350 passes; the sensors may participate in the measurement procedure bysupplying values of the monitored quantities exemplified above, orsupplying values of other physical quantities from which software 3311,3331 may compute or estimate the monitored quantities. The reconfiguringof the OTT connection 3350 may include message format, retransmissionsettings, preferred routing etc.; the reconfiguring need not affect thebase station 3320, and it may be unknown or imperceptible to the basestation 3320. Such procedures and functionalities may be known andpracticed in the art. In certain embodiments, measurements may involveproprietary UE signaling facilitating the host computer's 3310measurements of throughput, propagation times, latency and the like. Themeasurements may be implemented in that the software 3311, 3331 causesmessages to be transmitted, in particular empty or ‘dummy’ messages,using the OTT connection 3350 while it monitors propagation times,errors etc.

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 9 and FIG. 10. For simplicity of the presentdisclosure, only drawing references to FIG. 7 will be included in thissection. In a first action 3410 of the method, the host computerprovides user data. In an optional subaction 3411 of the first action3410, the host computer provides the user data by executing a hostapplication. In a second action 3420, the host computer initiates atransmission carrying the user data to the UE. In an optional thirdaction 3430, the base station transmits to the UE the user data whichwas carried in the transmission that the host computer initiated, inaccordance with the teachings of the embodiments described throughoutthis disclosure. In an optional fourth action 3440, the UE executes aclient application associated with the host application executed by thehost computer.

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 9 and FIG. 10. For simplicity of the presentdisclosure, only drawing references to FIG. 12 will be included in thissection. In a first action 3510 of the method, the host computerprovides user data. In an optional subaction (not shown) the hostcomputer provides the user data by executing a host application. In asecond action 3520, the host computer initiates a transmission carryingthe user data to the UE. The transmission may pass via the base station,in accordance with the teachings of the embodiments described throughoutthis disclosure. In an optional third action 3530, the UE receives theuser data carried in the transmission.

FIG. 13 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 9 and FIG. 10. For simplicity of the presentdisclosure, only drawing references to FIG. 13 will be included in thissection. In an optional first action 3610 of the method, the UE receivesinput data provided by the host computer. Additionally or alternatively,in an optional second action 3620, the UE provides user data. In anoptional subaction 3621 of the second action 3620, the UE provides theuser data by executing a client application. In a further optionalsubaction 3611 of the first action 3610, the UE executes a clientapplication which provides the user data in reaction to the receivedinput data provided by the host computer. In providing the user data,the executed client application may further consider user input receivedfrom the user. Regardless of the specific manner in which the user datawas provided, the UE initiates, in an optional third subaction 3630,transmission of the user data to the host computer. In a fourth action3640 of the method, the host computer receives the user data transmittedfrom the UE, in accordance with the teachings of the embodimentsdescribed throughout this disclosure.

FIG. 14 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 9 and FIG. 10. For simplicity of the presentdisclosure, only drawing references to FIG. 14 will be included in thissection. In an optional first action 3710 of the method, in accordancewith the teachings of the embodiments described throughout thisdisclosure, the base station receives user data from the UE. In anoptional second action 3720, the base station initiates transmission ofthe received user data to the host computer. In a third action 3730, thehost computer receives the user data carried in the transmissioninitiated by the base station.

When using the word “comprise” or “comprising” it shall be interpretedas non-limiting, i.e. meaning “consist at least of”.

The embodiments herein are not limited to the above described preferredembodiments. Various alternatives, modifications and equivalents may beused.

1. A method performed by a network node, for handling an outgoing mediacall of a user associated with multiple User Equipments, UEs, in acommunications network, the method comprising: receiving a request forthe outgoing media call to be set up from a first UE out of the multipleUEs, which request is obtained as a voice instruction from the user viaa Digital Assistant, DA, device, which voice instruction comprises apersonalized name associated with the first UE, identifying among themultiple UEs, the first UE and its associated IP Multimedia Subsystem,IMS, identifier based on the personalized name received in the voiceinstruction, sending to an IMS node, the identified IMS identifier ofthe first UE and a request to whether or not the first UE is registeredin the IMS node and supports media of the outgoing media call, when thefirst UE is registered in the IMS node and supports the media of theoutgoing media call, initiating the outgoing media call from the firstUE, and when the first UE is not registered in the IMS node and/or doesnot support the media of the outgoing media call, deciding how toproceed with the outgoing media call.
 2. The method according to claim1, wherein the request for the outgoing media call to be set up from afirst UE out of the multiple UEs further comprises an indication of amedia format of the media in the outgoing media call, which media formatis specified by the user in the voice instruction.
 3. The methodaccording to claim 1, wherein deciding how to proceed with the outgoingmedia call comprises instructing the DA device to offer the user to setup the outgoing media call on a second UE out of the multiple UEs. 4.The method according to, claim 1 wherein deciding how to proceed withthe outgoing media call comprises instructing the DA device to requestthe user to select an alternative UE among the multiple UEs to set upthe outgoing media call.
 5. The method according to claim 1, whereindeciding how to proceed with the incoming media call comprisesinstructing the DA device to tell the user that the pick-up of theincoming media call on the first UE is not possible.
 6. The methodaccording to claim 1 wherein the network node is represented by anapplication server node.
 7. The method according to claim 1, wherein therequest obtained as a voice instruction from the user further comprisesa request for the outgoing call to be set up via a first persona out ofmultiple personas associated with the user, wherein the voiceinstruction further comprises a personalized name associated with thefirst persona of the user.
 8. The method according to claim 7, wherein:identifying among the multiple UEs, the first UE and its associated IMSidentifier based on the personalized name received in the voiceinstruction, further comprises identifying among the multiple personasassociated with the user, an IMS user ID based on the personalized nameassociated with the first persona of the user received in the voiceinstruction, and wherein sending to the IMS node, the identified IMSidentifier of the first UE and a request to whether or not the first UEis registered in the IMS node and supports media of the outgoing mediacall, further comprises sending the identified IMS user ID to the IMSnode.
 9. A computer program product comprising a non-transitory computerreadable medium storing instructions, which when executed by aprocessor, causes the processor to perform actions according to claim 1.10. (canceled)
 11. A method performed by an Internet protocol MultimediaSubsystem, IMS, node, for handling an outgoing media call of a userassociated with at least one first User Equipment, UE, out of multipleUEs in a communications network, the method comprising: receiving, froma network node, an IMS identifier of the first UE and a request towhether or not the first UE is registered in the IMS node and supportsmedia of the outgoing media call, when the first UE is registered in theIMS node and supports the media of the outgoing media call, terminatingthe outgoing media call from the first UE, and when the first UE is notregistered in the IMS node and/or does not support the media of theoutgoing media call, sending a response to the network node, whichresponse comprises a message that the media call cannot be terminatedfrom the first UE.
 12. The method according to claim 11, furthercomprising: exposing to the network node, an Application ProgramInterface, API, comprising parameters associated with making a callsession related to the upcoming outgoing media call and requesting atleast IMS identifiers of the UEs.
 13. The method according to claim 12,wherein the API parameters comprise any one out of: intendedparticipants in the media call defined by corresponding User Identities,User IDs, wherein the User ID corresponds to an IMS Private Identity,IMS Private ID, and the respective IMS identifier defining any one outof the multiple UEs.
 14. The method according to claim 11, wherein therespective IMS identifier for any one out of the multiple UEs is anUniversally Unique Identifier, UUID, for the respective UE out of themultiple UEs.
 15. The method according to claim 11, wherein: receiving,from the network node, an IMS identifier of the first UE and a requestto whether or not the first UE is registered in the IMS node andsupports media of the outgoing media call further comprises receiving anIMS user ID associated with a first persona of the first user and arequest to whether or not the first persona of the user is registered inthe IMS node and supports the outgoing media call.
 16. The methodaccording to claim 15, further comprising: when the first UE isregistered in the IMS node and supports the media of the outgoing mediacall, and when the first persona of the user is registered in the IMSnode and supports the outgoing media call, terminating the outgoingmedia call from the first UE using the first persona, and when the firstUE is not registered in the IMS node and/or does not support the mediaof the outgoing media call and/or when the first persona of the user isnot registered in the IMS node and/or does not support the outgoingmedia call, sending a response to the network node, which responsecomprises a message that the media call cannot be terminated from thefirst UE using the first persona.
 17. A computer program productcomprising a non-transitory computer readable medium storinginstructions, which when executed by a processor, causes the processorto perform actions according to claim
 11. 18. (canceled)
 19. A networknode configured to handle an outgoing media call of a user associatedwith multiple User Equipments, UEs, in a communications network thenetwork node being further configured to: receive a request for theoutgoing media call to be set up from a first UE out of the multipleUEs, which request is adapted to be obtained as a voice instruction fromthe user via a Digital Assistant, DA, device, which voice instruction isadapted to comprise a personalized name associated with the first UE,identify among the multiple UEs, the first UE and its associated IPMultimedia Subsystem, IMS, identifier based on the personalized nameadapted to be received in the voice instruction, send to an IMS node,the identified IMS identifier of the first UE and a request to whetheror not the first UE is registered in the IMS node and is configured tosupport media of the outgoing media call, when the first UE isregistered in the IMS node and configured to support the media of theoutgoing media call, initiate the outgoing media call from the first UE,and when the first UE is not registered in the IMS node and/or is notconfigured to support the media of the outgoing media call, decide howto proceed with the outgoing media call.
 20. The network node accordingto claim 19, wherein the request for the outgoing media call to be setup from the first UE out of the multiple UEs is configured to comprisean indication of a media format of the media in the outgoing media call,which media format is adapted to be specified by the user in the voiceinstruction.
 21. The network node according to, claim 19, further beingconfigured to decide how to proceed with the outgoing media call byinstructing the DA device to offer the user to set up the outgoing mediacall on a second UE out of the multiple UEs.
 22. The network nodeaccording to, claim 19, further being configured to decide how toproceed with the outgoing media call by instructing the DA device torequest the user to select an alternative UE among the multiple UEs toset up the outgoing media call.
 23. The network node according to claim19, further being configured to decide how to proceed with the outgoingmedia call by instructing the DA device to tell the user that thepick-up of the incoming media call on the first UE is not possible 24.The network node according to claim 19, wherein the network node isadapted to be represented by an application server node.
 25. The networknode according to claim 19, wherein the request to the IMS node isadapted to comprise a request for the outgoing call to be set up via afirst persona out of multiple personas associated with the user, andwherein the voice instruction is further adapted to comprise apersonalized name associated with the first persona of the user.
 26. Thenetwork node according to claim 25, further being configured to:identify, among the multiple personas associated with the user, an IMSuser ID based on the personalized name associated with the first personaof the first user adapted to be received in the voice instruction, andsend the identified IMS user ID to the IMS node.
 27. An Internetprotocol Multimedia Subsystem, IMS, node configured to handle anoutgoing media call of a user associated with at least one first UserEquipment, UE, out of multiple UEs in a communications network, the IMSnode being further configured to: receive from a network node, an IMSidentifier of the first UE and a request to whether or not the first UEis registered in the IMS node and is configured to support media of theoutgoing media call, when the first UE is registered in the IMS node andis configured to support the media of the outgoing media call, terminatethe outgoing media call from the first UE, and when the first UE is notregistered in the IMS node and/or is not configured to support the mediaof the outgoing media call, send a response to the network node, whichresponse is configured to comprise a message that the media call cannotbe terminated from the first UE.
 28. The IMS node according to claim 27,further being configured to expose to the network node, an ApplicationProgram Interface, API, configured to comprise parameters associatedwith making a call session related to the upcoming outgoing media calland adapted to request at least IMS identifiers of the UEs.
 29. The IMSnode according to claim 28, wherein the API parameters are adapted tocomprise any one out of: intended participants in the media call adaptedto be defined by corresponding User Identities, User IDs, wherein theUser ID is adapted to correspond to an IMS Private Identity, IMS PrivateID, and the respective IMS identifier adapted to define any one out ofthe multiple UEs.
 30. The IMS node according to claim 27, wherein therespective IMS identifier for any one out of the multiple UEs is adaptedto be a Universally Unique Identifier, UUID, for the respective UE outof the multiple UEs.
 31. The IMS node according to claim 27, furtherbeing configured to receive from the network node: an IMS user IDconfigured to be associated with a first persona of the user, and arequest to whether or not the first persona of the user is registered inthe IMS node and is configured to support the outgoing media.
 32. TheIMS node according to claim 31, further being configured to: when thefirst UE is registered in the IMS node and supports the media of theoutgoing media call, and when the first persona of the user registeredin the IMS node and supports the outgoing media call, terminate theoutgoing media call from the first UE using the first persona, and whenthe first UE is not registered in the IMS node and/or does not supportthe media of the outgoing media call and/or when the first persona ofthe user is not registered in the IMS node and/or does not support theoutgoing media call, send a response to the network node, which responseis adapted to comprise a message that the media call cannot beterminated from the first UE using the first persona.